<h1>Getting started</h1>
<section>
      <a name="installing"></a>
      <h2>Installing</h2>

      <p>To use the MELPA repository, you'll need an Emacs with
        <code>package.el</code>, ie. Emacs 24.1 or greater.
      </p>

      <p>
        Enable installation of packages from MELPA by adding an entry
        to <code>package-archives</code> after <code>(require
        'package)</code> and before the call
        to <code>package-initialize</code> in
        your <code>init.el</code> or <code>.emacs</code> file:
      </p>

      <pre><code>(require 'package)
(let* ((no-ssl (and (memq system-type '(windows-nt ms-dos))
                    (not (gnutls-available-p))))
       (proto (if no-ssl "http" "https")))
  (when no-ssl (warn "\
Your version of Emacs does not support SSL connections,
which is unsafe because it allows man-in-the-middle attacks.
There are two things you can do about this warning:
1. Install an Emacs version that does support SSL and be safe.
2. Remove this warning from your init file so you won't see it again."))
  (add-to-list 'package-archives (cons "melpa" (concat proto "://melpa.org/packages/")) t)
  ;; Comment/uncomment this line to enable MELPA Stable if desired.  See `package-archive-priorities`
  ;; and `package-pinned-packages`. Most users will not need or want to do this.
  ;;(add-to-list 'package-archives (cons "melpa-stable" (concat proto "://stable.melpa.org/packages/")) t)
  )
(package-initialize)</code></pre>

      <p>
        Note that you'll need to run <code>M-x package-refresh-contents</code> or
        <code>M-x package-list-packages</code> to ensure that Emacs has fetched
        the MELPA package list before you can install packages with
        <code>M-x package-install</code> or similar.
      </p>

      <p>
        To use the <a href="https://stable.melpa.org" title="MELPA Stable">
          stable package repository</a> instead of the default
        “bleeding-edge” repository, use this instead
        of <code>"melpa"</code>:
      </p>

      <pre><code>(add-to-list 'package-archives
             '("melpa-stable" . "https://stable.melpa.org/packages/") t)</code></pre>

      <p>
        <strong>Note:</strong> <em>There are some problems using the
          <code>https</code> location with Emacs on Windows. There is
          currently no known easy fix for this. You can still use MELPA
          by using the non-SSL location by replacing <code>https</code>
          with <code>http</code>.</em>
      </p>
      <h3>Customizations</h3>
      <p>
        What if you only want some of your packages to be installed
        from MELPA, and the rest from Marmalade or elsewhere?
      </p>
      <p>
        In Emacs 24.4 and later, <code>package-pinned-packages</code>
        allows you to exclude or include versions according to their
        source. For users using older versions of Emacs, we provide
        a <code>package-filter.el</code> package (available in MELPA)
        that will allow you to enable only certain packages or exclude
        certain packages.  You can install the package manually by
        pasting this into your <code>*scratch*</code> buffer and
        evaluating it.
      </p>
      <pre><code>(progn
  (switch-to-buffer
    (url-retrieve-synchronously
      "https://raw.github.com/melpa/package-filter/master/package-filter.el"))
  (package-install-from-buffer  (package-buffer-info) 'single))</code></pre>

      <p>You can then customize two variables:</p>
      <dl>
        <dt><code>package-archive-enable-alist</code></dt>
        <dd>
          <p>
            Optional Alist of enabled packages used
            by <code>package-filter</code>. The format
            is <code>(ARCHIVE . PACKAGE ...)</code>,
            where <code>ARCHIVE</code> is a string matching an archive
            name in<code>package-archives</code>, <code>PACKAGE</code>
            is a symbol of a package in <code>ARCHIVE</code> to
            enable.
          </p>
          <p>
            If no <code>ARCHIVE</code> exists in the alist, all
            packages are enabled.
          </p>
        </dd>
        <dt><code>package-archive-exclude-alist</code></dt>
        <dd>
          <p>
            Alist of packages excluded by <code> package-filter
            </code>. The format is <code>(ARCHIVE . PACKAGE
            ...)</code>, where <code>ARCHIVE</code> is a string
            matching an archive name
            in</code>package-archives</code>, <code>PACKAGE</code> is
            a symbol of a package in that archive to exclude.</p>
          <p>
            Any specified package is excluded regardless of the value
            of <code>package-archive-enable-alist</code>
          </p>
        </dd>
      </dl>
    </section>
    <section>
      <a name="known-issues"></a>
      <h2>Known Issues</h2>
      <p>
        <strong>Note:</strong> <em>These fixes are included in
        the <code>package-filter.el</code> package.</em>
      </p>
      <p>
        There is a small bug in Emacs 24’s <code>package.el</code> such
        that the dependency order comes out backwards. The problem is
        patched by some <em>advice</em>.
      </p>

      <pre><code> (defadvice package-compute-transaction
  (before package-compute-transaction-reverse (package-list requirements) activate compile)
    "reverse the requirements"
    (setq requirements (reverse requirements))
    (print requirements))</code></pre>
    </section>
    <section>
      <a name="updating"></a>
      <h2>Updating Packages</h2>
      <p>
        After running <code>package-list-packages</code>,
        type <em>U</em> (mark Upgradable packages) and then <em>x</em>
        (eXecute the installs and deletions). When it’s done
        installing all the packages it will ask if you want to delete
        the obsolete packages and so you can hit <em>y</em> (Yes).
      </p>
      <p>
        If you run into a problem installing or upgrading, you may
        need to go into your <code>~/.emacs.d/elpa/</code> directory
        and delete packages that are installed multiple times. This
        can happen when the install times out.
      </p>
      <a name="adding"></a>
      <h2>Adding a Package</h2>
      <p>
	In so many words, fork the project's source tree
	and create a pull request with a recipe for your package.
	The <tt>README.md</tt> file on GitHub has more details.
	See the next section for a link.
      </p>
      <a name="development"></a>
      <h2>Development</h2>
      <p><a href="https://github.com/melpa/melpa">https://github.com/melpa/melpa</a></p>
      <p>
        Contributions are welcome. Currently, the builder supports
        packages using Git, Mercurial, and EmacsWiki (deprecated
        due to security concerns). Support for Bazaar, CVS, Darcs,
        Fossil and Subversion has been removed due to very limited
        use.
      </p>
    </section>
